Skip to content

Conversation

@picandocodigo
Copy link
Member

This was proposed in elastic/elasticsearch#97613 (comment).
Opening this as a Draft to check with the rest of the Devtools team about this and see if it still makes sense and if all clients support the OPTIONS method.

Let me know, otherwise we can close this PR and the original issue.

@picandocodigo picandocodigo requested a review from a team August 13, 2025 14:53
@github-actions
Copy link
Contributor

Following you can find the validation changes against the target branch for the APIs.

No changes detected.

You can validate these APIs yourself by using the make validate target.

@picandocodigo picandocodigo added the skip-backport This pull request should not be backported label Aug 13, 2025
@l-trotta
Copy link
Contributor

np for java

@pquentin
Copy link
Member

pquentin commented Aug 19, 2025

It's also fine for Python. Actually ping is custom there, so I can make the changes independently of the specification.

Notice how this adds an error: we'll need to add it to https://github.com/elastic/elasticsearch/blob/main/rest-api-spec/src/main/resources/rest-api-spec/api/ping.json first. It's also fine to allow both HEAD and OPTIONS, and the generators can choose the best version as they see fit.

@picandocodigo
Copy link
Member Author

Thanks!
Opened the PR in Elasticsearch:
elastic/elasticsearch#133122

@picandocodigo
Copy link
Member Author

Not moving forward with this after discussing with the team.

@pquentin pquentin deleted the options_ping branch October 29, 2025 07:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

skip-backport This pull request should not be backported specification

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants